LINK-10

LINK-10 is a linking loader; it takes .REL files and makes .DMP files
and  core images.   LINK-10 is  much faster  than the LOADER  if many
global symbols are  being loaded, because LINK-10  uses a hash  table
for  the global  symbols  and the  LOADER  uses a  linear  list.   At
Stanford LINK-10 runs with a 20K sharable upper segment.  The name of
the file containing LINK-10 is LINK.DMP[1,3].  The text of long error
messages is kept in LINK.ERR[1,3].

The command syntax for LINK-10 is different from that of the LOADER. 
The  following examples  should help to  ease conversion  from LOADER
commands to the  corresponding LINK-10 commands.   For more  complete
information, consult the DEC documentation on LINK-10. 

Load, no .DMP file, no execute, no symbols, no DDT:
    LOADER	*/YFOO<alt>

    LINK-10	*=SYS:SAILOW,FOO/G<cr>

Load, create a .DMP file, load RAID and sorted local symbols:
    LOADER	*/Y/VFOO<cr>
		*FOO↑/E<alt>

    LINK-10	*FOO/SAV=SYS:SAILOW,SYS:RAID,/L FOO/E/G<cr>
	(/L is an abbreviation of /LOCALS; /E means /EXECUTE;
	 /G means /GO--terminate command scanning and start loading.
	 To skip the sorting of the symbol table, /SYSORT:NORAID.)

Load from indirect file:
    LOADER	*LODCMD.CMD@<cr>

    LINK-10	*@LODCMD.CMD<cr>

Device names are NOT sticky in LINK-10.

To continue a LINK-10  command over more than one line,  type a minus
sign  <-> as the  last character  of all lines  but the last.   While
scanning a continued line, the LINK-10 prompt is <#>. 

drf - 9/11/82 - There are two bugs in LINK that show up on large programs.
First, LINK might write a DMP file that is not long enough for WAITS'
taste.  The remedy is to
R LINK
=FOO/G
File too big....saved as 000LNK.DMP
GET 000LNK 432
SSAVE FOO
...where you'll have to play around to get the right number to use instead
of 432.

The other problem is that LINK tries to sort the symbol table, even if it
has already written it out to a temporary file.  The way around this is
to say
R LINK
=FOO/SYSORT:NORAID/G